The raid command node enables you to control RAID devices. The raid command node includes the following subnode commands:
bbu
controllers
diskdrives
enclosures
schedules
sets
subsystems
Each of the subnode commands, and the leaf-node commands attached to them, are described in detail, with parameters and arguments listed for each command.
Examples of command usage are included in the discussions.
Note: The information in this chapter applies only to SpinStor storage. This information does not apply to Network Appliance FAS270c storage or to any third-party vendors' storage. For information on managing LUNs on Network Appliance storage, see the FAS270c documentation.
Note: The raid commands report the sizes of disk drives in gigabytes; however, the commands interpret “gigabyte” as 230 (1,073,741,824) bytes, not one billion bytes. Most disk-drive manufacturers interpret “gigabyte” as one billion bytes, so there can be a discrepancy between the output of the commands and the label on the disk. For instance, the commands can report a 36-GB drive as having a physical size of 34 GB.
To manage the battery backup unit, use the following raid bbu commands.
fastcharge
modify
recondition
show
stop
CLI:
raid bbu fastcharge -deviceid device_ID
GUI: Navigate to the RAID → Battery Backup Unit node, then select a BBU from the table and run the Fast Charge command from the drop-down menu of the action pane.
The raid bbu fastcharge command identifies a battery backup unit and initiates a fast charge on the BBU. Recharging a BBU takes several hours.
-deviceid device_ID
The device identification is in the format rsubsystem_numberbbattery_ID, where subsystem_number indicates the ID of the RAID subsystem and battery_ID indicates the ID of the battery.
The following command example identifies battery backup unit r0b1 and initiates a fast charge on the BBU.
spinserver::> raid bbu fastcharge -deviceid r0b1
CLI:
raid bbu modify -deviceid device_ID -threshold threshold
GUI: Navigate to the RAID → Battery Backup Unit node, then select a BBU from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The raid bbu modify command changes the minimum low-power threshold of the specified BBU to the level specified by the -threshold parameter. The threshold is expressed in minutes of charge that the BBU can hold. If the power level drops below this threshold, an alarm is triggered.
-deviceid device_ID
The device identification is in the format rsubsystem_numberbbattery_ID, where subsystem_number indicates the ID of the RAID subsystem and battery_ID indicates the ID of the battery.
-threshold threshold
This is the minimum low-power threshold setting of the BBU, specified in minutes.
The following command example changes the minimum low-power threshold to 1200 minutes for BBU r0b1.
spinserver::> raid bbu modify -deviceid r0b1 -threshold 1200
CLI:
raid bbu recondition -deviceid device_ID
GUI: Navigate to the RAID → Battery Backup Unit node, then select the appropriate BBU from the table and run the Recondition command from the drop-down menu of the action pane.
The raid bbu recondition command identifies a battery backup unit and designates it for reconditioning. Reconditioning is a full discharge and recharge of the BBU; the process takes several hours to complete.
The reconditioning cycle must be completed without an interruption of power. Also, do not interrupt the reconditioning cycle by using the raid bbu stop command to stop the reconditioning process. If the cycle is interrupted for any reason, the battery must be recharged and the reconditioning process restarted.
-deviceid device_ID
The device identification is in the format rsubsystem_numberbbattery_ID, where subsystem_number indicates the ID of the RAID subsystem and battery_ID indicates the ID of the battery.
The following command example identifies BBU r0b1 and starts the reconditioning process.
spinserver::> raid bbu recondition -deviceid r0b1
CLI:
raid bbu show [-deviceid device_ID]
GUI: Navigate to the RAID → Battery Backup Unit node. To display information about a specific BBU, select it from the table and run the Show command from the drop-down menu in the action pane.
The raid bbu show command displays information about one or more BBUs. Issue the command without a parameter to display information about all BBUs in the system, or with the -deviceid parameter to display information about a specific BBU. The command displays the following information about the BBU or BBUs:
Device ID
Type
Version
Status
Current power, listed in minutes
Maximum power
Charge level (%)
Low-power threshold. The threshold is expressed in minutes of charge that the BBU can hold. If the power level drops below this threshold, an alarm is triggered.
[-deviceid device_ID]
The device identification is in the format rsubsystem_numberbbattery_ID, where subsystem_number indicates the ID of the RAID subsystem and battery_ID indicates the ID of the battery.
The following command example displays information about battery backup unit r0b1.
spinserver::> raid bbu show -deviceid r0b1
CLI:
raid bbu stop -deviceid device_ID
GUI: Navigate to the RAID → Battery Backup Unit node, then select the appropriate BBU from the table and run the Stop Recondition command from the drop-down menu of the action pane.
The raid bbu stop command identifies a battery backup unit and halts its reconditioning process.
Note: If the reconditioning of a BBU is stopped, the reconditioning cycle must be restarted and completed before the BBU can be used again. The reconditioning cycle takes several hours to complete.
-deviceid device_ID
The device identification is in the format rsubsystem_numberbbattery_ID, where subsystem_number indicates the ID of the RAID subsystem and battery_ID indicates the ID of the battery.
The following command example stops the reconditioning process on the battery backup unit named r0b1.
spinserver::> raid bbu stop -deviceid r0b1
To manage the RAID controllers in a RAID subsystem, use the following raid controllers commands.
setpartneroffline
setpartneronline
show
updatefirmware
CLI:
raid controllers setpartneroffline -deviceid device_ID
GUI: Navigate to the RAID → RAID Controllers node, then select the appropriate controller from the table and run the Offline Partner command from the drop-down menu of the action pane.
The raid controllers setpartneroffline command takes a RAID controller's partner offline.
-deviceid device_ID
The ID of the controller is in the format rsubsystem_numberccontroller_number, where subsystem_number indicates the ID of the RAID subsystem and controller_number indicates the specific RAID controller.
Note: Be sure to use the device ID of the RAID controller whose partner you want to take offline, and not the device ID of the RAID controller that you actually want to take offline.
The following command example takes the partner of RAID controller r0c1 offline.
spinserver::> raid controllers setpartneroffline -deviceid r0c1
CLI:
raid controllers setpartneronline -deviceid device_ID
GUI: Navigate to the RAID → RAID Controllers node, then select the appropriate controller from the table and run the Online Partner command from the drop-down menu of the action pane.
-deviceid device_ID
The ID of the controller is in the format rsubsystem_numberccontroller_number, where subsystem_number indicates the ID of the RAID subsystem and controller_number indicates the specific RAID controller.
Note: Be sure to use the device ID of the RAID controller whose partner you want to set online, and not the device ID of the RAID controller you want to set online.
The following command example sets the partner of RAID controller r0c1 online.
spinserver::> raid controllers setpartneronline -deviceid r0c1
CLI:
raid controllers show [-deviceid device_ID]
GUI: Navigate to the RAID → RAID Controllers node. To display information about a specific controller, select it from the table and run the Show command from the drop-down menu of the action pane.
The raid controllers show command displays information about one RAID controller or all RAID controllers in the system. After identification is made, the following information about the RAID controller or controllers is displayed:
Device ID
Status
Model
Firmware version
RAID subsystem ID
Disk enclosure ID
World Wide Name
Cache size (in MB)
Memory size (in MB)
BBU status
Number of host ports
Number of drive channels
Bus type
Bus width
Bus speed (in MB per second)
Number of physical devices
Number of logical devices
Partner status
Fault tolerance status
Port device name
Number of port IDs
To display information about one RAID controller, use the command with the -deviceid parameter. To display a list of all RAID controllers in the system, use no parameters.
[-deviceid device_ID]
The ID of the RAID controller is in the format rsubsystem_numberccontroller_number, where subsystem_number indicates the ID of the RAID subsystem and controller_number indicates the specific RAID controller.
The following command example, which uses no parameters, displays information about all RAID controllers in a RAID subsystem.
spinserver::> raid controllers show
Device ID Status Model Version Partner
r0c0 Active FFx 7.85 Active
r0c1 Active FFx 7.85 Active
CLI:
raid controllers updatefirmware -deviceid device_ID -imagefile path
GUI: Navigate to the RAID → RAID Controllers node, then select the appropriate controller from the table and run the Update Firmware command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed and click Update Firmware.
The raid controllers updatefirmware command updates a RAID controller's firmware. Running the command updates the firmware on both RAID controllers in a RAID subsystem, so the command needs to be run on only one controller in a RAID subsystem.
-deviceid device_ID
The ID of the controller is in the format rsubsystem_numberccontroller_number, where subsystem_number indicates the ID of the RAID subsystem and controller_number indicates the specific RAID controller.
-imagefile path
The image file path is the absolute path name to the updated RAID controller firmware image.
The following command updates the firmware for RAID controller r0c1 from an image file located at /usr/ima/spin.ima.
spinserver::> raid controllers updatefirmware -deviceid r0c1 -imagefile /usr/ima/spin.ima
To manage disk drives, use the following raid diskdrives commands:
checksense
firmwareupdatestatus
locate
makehotspare
makeoffline
makeonline
prepareforremoval
selftest
selfteststatus
show
stopselftest
updatefirmware
CLI:
raid diskdrives checksense -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Check Sense command from the drop-down menu of the action pane.
The raid diskdrives checksense command displays SCSI sense data for the specified disk drive. SCSI sense data provides information about a SCSI device's current status. See your SCSI documentation for information about SCSI event codes and status.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following example displays the SCSI sense data of disk drive r0d14.
spinserver::> raid diskdrives checksense -deviceid r0d14 Action "Check Sense" returned with the following status: 70 00 00 02 22 ed fb 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CLI:
raid diskdrives firmwareupdatestatus -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Firmware Update Status command from the drop-down menu of the action pane.
The raid diskdrives firmwareupdatestatus command checks the degree of completion of a firmware upgrade of a specific disk drive.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example checks the degree of completion of the firmware upgrade of disk drive r0d14.
spinserver::> raid diskdrives firmwareupdatestatus -deviceid r0d14
CLI:
raid diskdrives locate -deviceid device_ID -time minutes
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Locate command from the drop-down menu of the action pane. Enter the appropriate value into the table that is displayed and click Locate.
The raid diskdrives locate command locates a disk in a RAID subsystem. The front panel LED of the disk blinks for the length of time specified in the command to indicate the location of the disk in the disk enclosure.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
-time minutes
This specifies the number of minutes the disk drive's LED flashes. The default is 0 (zero). When the default setting is used, the disk drive's LED flashes for less than a minute.
The following command example locates disk r0d14 in the disk enclosure and flashes its LED for 2 minutes.
spinserver::> raid diskdrives locate -deviceid r0d14 -time 2
CLI:
raid diskdrives makehotspare -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Hot Spare command from the drop-down menu of the action pane.
The raid diskdrives makehotspare command identifies a disk by its disk ID and designates it as a hot spare. A hot spare is a disk in a RAID subsystem that automatically replaces a disk that has failed.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example designates disk r0d14 as a hot spare.
spinserver::> raid diskdrives makehotspare -deviceid r0d14
CLI:
raid diskdrives makeoffline -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the OffLine command from the drop-down menu of the action pane.
The raid diskdrives makeoffline command identifies a disk by its disk ID and takes it offline.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example takes disk r0d14 offline.
spinserver::> raid diskdrives makeoffline -deviceid r0d14
CLI:
raid diskdrives makeonline -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the OnLine command from the drop-down menu of the action pane.
The raid diskdrives makeonline command identifies a disk by its disk ID and brings it online.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example brings disk r0d14 online.
spinserver::> raid diskdrives makeonline -deviceid r0d14
CLI:
raid diskdrives prepareforremoval -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Prepare for Removal command from the drop-down menu of the action pane.
The raid diskdrives prepareforremoval command identifies a disk drive by its ID and prepares it for removal from the disk enclosure.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example prepares disk r0d14 for physical removal from the disk enclosure.
spinserver::> raid diskdrives prepareforremoval -deviceid r0d14
CLI:
raid diskdrives selftest -deviceid device_ID -options options
GUI: Navigate to the RAID → Disk Drives node, then select a disk drive from the table and run the Self-test command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed and click Self-test.
The raid diskdrives selftest command identifies a disk by its ID and performs a status check on the disk.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
-options options
This specifies the options for the disk's self-test. Use default as the value of this parameter unless instructed to do otherwise by the Network Appliance Technical Support.
The following command example performs a status check on disk r0d14, using default options.
spinserver::> raid diskdrives selftest -deviceid r0d14 -options default
CLI:
raid diskdrives selfteststatus -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select a disk drive from the table and run the Self-test Status command from the drop-down menu of the action pane.
The raid diskdrives selfteststatus command identifies a disk by its ID and checks the status of a self-test of a physical disk in a RAID subsystem.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example checks the status of a self-test of disk r0d14.
spinserver::> raid diskdrives selfteststatus -deviceid r0d14 Action "Self-test Status" returned with the following status: Success
CLI:
raid diskdrives show [-deviceid device_ID]
GUI: Navigate to the RAID → Disk Drives node. To display information about a specific disk drive, select it from the table and run the Show command from the drop-down menu of the action pane.
The raid diskdrives show command displays the following information about one disk drive or all disk drives in the RAID subsystem:
Device ID
Vendor's name
Model
Revision
Speed
Configured size or capacity
Status (online, offline, or hot spare)
The RAID set that is using the disk
RAID subsystem
Enclosure and slot number
Disk channel number
Disk target number
Bus width
Negotiating bus width
ANSI version
Sync status
Linked status
Command queue status
SMART status
Physical size
Serial number
To display information about one disk drive, use the command with the -deviceid parameter. To display a list of all disk drives in the RAID subsystem, use no parameter.
[-deviceid device_ID]
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example displays information about all of the disks in a system.
spinserver::> raid diskdrives show Device ID Capacity Status Used By Channel Target r0d1 33 GB Online r0s0 1 0 r0d10 33 GB Online r0s1 0 5 r0d13 33 GB Online r0s1 1 6 r0d14 33 GB Online r0s1 0 7 r0d17 33 GB Online r0s1 1 8 r0d18 33 GB Online r0s1 0 9 r0d2 33 GB Online r0s0 0 1 r0d21 33 GB Online r0s2 1 10 r0d22 33 GB Online r0s2 0 11 r0d25 33 GB Online r0s2 1 12 r0d26 33 GB Online r0s2 0 13 r0d29 33 GB Online r0s2 1 14 r0d5 33 GB Online r0s0 1 2 r0d6 33 GB Online r0s0 0 3 r0d9 33 GB Online r0s0 1 4 r1d33 33 GB Online r1s3 1 16 r1d34 33 GB Online r1s3 0 17 r1d37 33 GB Online r1s3 1 18 r1d38 33 GB Online r1s3 0 19 r1d41 33 GB Online r1s3 1 20 r1d42 33 GB Online r1s4 0 21 -- Type 'q' to quit and any key to continue --
The following example displays information about disk r0d1.
spinserver::> raid diskdrives show -deviceid r0d1 Device ID r0d1 Vendor SEAGATE Model ST336752FC Revision 0003 Speed Async Speed Capacity 33 GB Status Online Used By r0s0 RAID Subsystem r0 Enclosure r0e1, slot 0 Channel 1 Target 0 Bus Width 8 bits Nego. Bus Width 1 bit ANSI Version SCSI-3 Sync true Linked true CmdQue true SMART? true Phys. Size 34 GB Serial Number 3ET01SKJ
CLI:
raid diskdrives stopselftest -deviceid device_ID
GUI: Navigate to the RAID → Disk Drives node, then select the appropriate disk drive from the table and run the Stop Self-test command from the drop-down menu of the action pane.
The raid diskdrives stopselftest command identifies a disk by its ID and stops the self-test of the disk.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
The following command example stops the self-test of disk r0d14.
spinserver::> raid diskdrives stopselftest -deviceid r0d14
CLI:
raid diskdrives updatefirmware -deviceid device_ID -imagefile path
GUI: Navigate to the RAID → Disk Drives node, then select a disk drive from the table and run the Update Firmware command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed and click Update Firmware.
The raid diskdrives updatefirmware command updates the firmware of a disk drive in a RAID subsystem from the specified firmware image file.
-deviceid device_ID
The ID of the disk is in the format rsubsystem_numberddiskdrive_number, where subsystem_number indicates the ID of the RAID subsystem and diskdrive_number indicates the ID of the specific disk drive.
-imagefile path
This is the absolute path name to a disk-drive firmware image.
The following example updates the firmware on disk drive r0d14 from an image located at /usr/ima/spin.ima.
spinserver::> raid diskdrives updatefirmware -deviceid r0d14 -imagefile /usr/ima/spin.ima
To manage RAID or expansion JBOD enclosures, use the following raid enclosures commands:
locate
mute
show
CLI:
raid enclosures locate -deviceid device_ID -time minutes
GUI: Navigate to the RAID → Disk Enclosures node, then select an enclosure from the table and run the Locate command from the drop-down menu of the action pane.
The raid enclosures locate command locates the specified disk enclosure by making all of the LEDs on the disk enclosure flash.
-deviceid device_ID
The ID of the enclosure is in the format rsubsystem_numbereenclosure_number, where subsystem_number indicates the RAID subsystem and enclosure_number indicates the specific enclosure.
-time minutes
This specifies the number of minutes the disk enclosure's LEDs flash. The default is 0 (zero). When the default setting is used, the disk drive enclosure's LEDs flash for less than a minute.
The following command locates the disk enclosure named r0e1 by making all of the LEDs on the enclosure flash for 2 minutes.
spinserver::> raid enclosures locate -deviceid r0e1 -time 2
CLI:
raid enclosures mute -deviceid device_ID
GUI: Navigate to the RAID → Disk Enclosures node, then select an enclosure from the table and run the Mute command from the drop-down menu of the action pane.
The raid enclosures mute command silences the alarm on a disk enclosure that is triggered in the event of an error.
-deviceid device_ID
The ID of the enclosure is in the format rsubsystem_numbereenclosure_number, where subsystem_number indicates the RAID subsystem and enclosure_number indicates the specific enclosure.
The following command silences the alarm on disk enclosure r0e1.
spinserver::> raid enclosures mute -deviceid r0e1
CLI:
raid enclosures show [-deviceid device_ID]
GUI: Navigate to the RAID → Disk Enclosures node. To display information about a specific enclosure, select it from the table and run the Show command from the drop-down menu of the action pane.
The raid enclosures show command displays information about one disk enclosure or all disk enclosures in a system. To display information about one disk enclosure, use the command with the -deviceid parameter. To display a list of all enclosures in the RAID subsystem, use no parameters. The command displays the following information about the disk enclosure or enclosures:
Device ID
Status
Manufacturer's name
Model
RAID subsystem number
World Wide Name
Service type
Number of disk slots
Controller access
Fan status
Power status
Temperature status
Alarm status
UPS status
Daisy-chain status (true or false)
System type (RAID or JBOD)
Alarm-enablement status (true or false)
[-deviceid device_ID]
The ID of the enclosure is in the format of rsubsystem_numbereenclosure_number, where subsystem_number indicates the RAID subsystem and enclosure_number indicates the specific enclosure.
The following command example uses no parameters and displays information about all disk enclosures in a system.
spinserver::> raid enclosures show Device ID Model Status Access Type r0e1 FR15-F22-2SM3. OK OK SES r1e1 FR15-F22-2Sxx. OK OK SES r1e2 FR15-F22-2SM3. OK OK SES
The following example displays information about the disk enclosure named r0e1.
spinserver::> raid enclosures show -deviceid r0e1 Device ID r0e1 Status OK Manufacturer JMR ELEC Model FR15-F22-2SM3. Array r0 WWN 01 00 03 00 00 00 ad 00 Service Type SES Slots 15 Access OK Fans 0 OK High, 1 OK High Power 0 OK, 1 OK Temp 0 OK 40C Alarm 0 OK OFF UPS 0 OK Daisy Chained? true System Type RAID Alarm Enabled true
To schedule regular operations on RAID components, use the following raid schedules commands:
delete
modify
new
show
CLI:
raid schedules delete -name schedule_name
GUI: Navigate to the RAID → Schedules node, then select the appropriate schedule from the table and run the Delete command from the drop-down menu of the action pane.
The following command example deletes a RAID schedule named raid.sched.1.
spinserver::> raid schedules delete -name raid.sched.1
CLI:
raid schedules modify -name schedule_name -enabled {true | false}
GUI: Navigate to the RAID → Schedules node, then select the appropriate schedule from the table and run the Modify command from the drop-down menu of the action pane. Enter the appropriate value into the table that is displayed, then click Modify.
-name schedule_name
This specifies the name of the RAID schedule that is to be enabled or disabled.
-enabled {true | false}
This specifies whether the schedule is enabled (true) or disabled (false).
The following command example disables a RAID schedule named raid.sched.1.
spinserver::> raid schedules modify -name raid.sched.1 -enabled false
CLI:
raid schedules new -name schedule_name -raidaction action_name -devices device_name_or_pattern -schedule {#-Minutely | hourly | daily | weekly | monthly | yearly} -enabled {true | false}
GUI: Navigate to the RAID → Schedules node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
The raid schedules new command creates a RAID schedule. A schedule consists of a schedule name, an action to be performed, the device or devices on which the action is performed, and the time interval at which the action is performed. The schedule can initially be enabled or disabled.
-name schedule_name
This specifies the name of the RAID schedule that is to be created.
-raidaction action_name
This specifies the action that is to be performed. Currently, the only accepted value is ConsistencyCheck for a RAID consistency check.
-devices device_name_or_pattern
This specifies the device or devices on which the action is performed. This can either be the name of a single device (for example, r1s0) or a pattern to specify multiple devices (for example, r1s* to specify all RAID sets).
-schedule {#-Minutely | hourly | daily | weekly | monthly | yearly}
This specifies the time interval at which the action is performed.
-enabled {true | false}
This specifies whether the schedule is enabled (true) or disabled (false).
The following command example creates a RAID schedule named raid.sched.1. It runs a consistency check on all devices named r1s* on a daily basis. It is enabled.
spinserver::> raid schedules new -name raid.sched.1 -raidaction ConsistencyCheck -devices r1s* -schedule daily -enabled true
CLI:
raid schedules show [-name schedule_name]
GUI: Navigate to the RAID → Schedules node. To display information about a specific RAID set, select it from the table and run the Show command from the drop-down menu in the action pane.
The raid schedules show command displays the following information. Specify the -name parameter to display information about a single schedule; otherwise, the command displays information about all known schedules.
Schedule name
Action
Device or devices
Schedule (time interval)
Whether or not the schedule is enabled
Time of next execution (GUI only)
Time of last execution
The following command example displays information about all RAID schedules.
spinserver::> raid schedules show Name Action Devices Schedule Enabled? Last Execution raid.sched.1 ConsistencyCheck r0s6 weekly true
To manage RAID sets, use the following raid sets commands.
bkginitstatus
consistencycheckstatus
delete
initstatus
locate
makeoffline
makeonline
modify
new
rebuildstatus
show
show-disks
startbkginit
startconsistencycheck
startinit
startrebuild
stopbkginit
stopconsistencycheck
stopinit
stoprebuild
CLI:
raid sets bkginitstatus -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Background Init Status command from the drop-down menu of the action pane.
The raid sets bkginitstatus command identifies a RAID set by the device ID assigned to it. After identification is made, the degree of completion of the background initialization of a RAID set is displayed.
Note: The raid sets bkginitstatus command works only if background initialization is enabled (background initialization is the default).
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and queries its background initialization status.
spinserver::> raid sets bkginitstatus -deviceid r0s0
CLI:
raid sets consistencycheckstatus -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Consistency Check Status command from the drop-down menu of the action pane.
The raid sets consistencycheckstatus command identifies a RAID set by the device ID assigned to it. After identification is made, the degree of completion of the consistency check of a RAID set is displayed.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and queries the status of its consistency check.
spinserver::> raid sets consistencycheckstatus -deviceid r0s0 Action "Consistency Check Status" returned with the following status: Not in progress
CLI:
raid sets delete -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Delete command from the drop-down menu of the action pane.
The raid sets delete command identifies a RAID set by the device ID assigned to it. After identification is made, the RAID set is removed from the RAID subsystem.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and removes it from the RAID subsystem.
spinserver::> raid sets delete -deviceid r0s0
CLI:
raid sets initstatus -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Initialization Status command from the drop-down menu of the action pane.
The raid sets initstatus command identifies a RAID set by the device ID assigned to it. After identification is made, the degree of completion of the initialization of a RAID set is displayed.
Note: Background initialization is enabled by default. Use this command only when background initialization is disabled. When background initialization is enabled, use the raid sets bkginitstatus command.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and queries the status of its initialization.
spinserver::> raid sets initstatus -deviceid r0s0 Action "Initialization Status" returned with the following status: Not in progress
CLI:
raid sets locate -deviceid device_ID -time minutes
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Locate command from the drop-down menu of the action pane. Enter the appropriate value into the table that is displayed and click Locate.
The raid sets locate command identifies a RAID set by the device ID assigned to it. After identification is made, the command causes the front-panel LEDs of the disks in the RAID set to blink for the length of time specified.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
-time minutes
This specifies the number of minutes for which the LED is to blink.
The following command example identifies RAID set r0s0 and causes all of the disks in the RAID set to blink their front-panel LEDs for 2 minutes.
spinserver::> raid sets locate -deviceid r0s0 -time 2
CLI:
raid sets makeoffline -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the OffLine command from the drop-down menu of the action pane.
The raid sets makeoffline command identifies a RAID set by the device ID assigned to it. After identification is made, the RAID set is taken offline.
Note: This command is used when you need to move the disks in a RAID set from one disk enclosure to another, or if you need to perform disk maintenance on more than one disk in a RAID set.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and takes it offline.
spinserver::> raid sets makeoffline -deviceid r0s0
CLI:
raid sets makeonline -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the OnLine command from the drop-down menu of the action pane.
The raid sets makeonline command identifies a RAID set by the device ID assigned to it. After identification is made, the command brings the RAID set online.
Note: The raid sets makeonline command is used to bring a RAID set back online after the raid sets makeoffline command has been used to take the RAID set offline. If the RAID set is already online, using the raid sets makeonline command has no effect.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and brings it online.
spinserver::> raid sets makeonline -deviceid r0s0
CLI:
raid sets modify -deviceid device_ID -writecacheenabled {true | false}
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The raid sets modify command identifies a RAID set by the device ID assigned to it. After identification is made, the write cache is either enabled or disabled. The default is disabled.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
-writecacheenabled {true | false}
To enable the write cache, use true as the argument. To disable the write cache, use false as the argument. The default setting is false.
The following command example identifies RAID set r0s0 and enables its write cache.
spinserver::> raid sets modify -deviceid r0s0 -writecacheenabled true
CLI:
raid sets new -raidlevel { 0 | 1 | 3 | 5 | 0+1 } -stripsize { 8 | 16 | 32 | 64 } -writecacheenabled {true | false} -status RAID_status -disks [list_of_disks]
GUI: Navigate to the RAID → RAID Sets node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
The raid sets new command creates a RAID set conforming to the values specified in the command options.
-raidlevel { 0 | 1 | 3 | 5 | 0+1 }
The RAID set level is the type of RAID on the RAID set. The following values are supported: 0, 1, 3, 5, and 0+1. The default is 5.
-stripsize { 8 | 16 | 32 | 64 }
The default RAID set strip size is 32 KB. Other possible sizes are 8 KB, 16 KB, or 64 KB. A RAID strip is a piece of a single disk that is used for data storage. A RAID stripe is a set of the corresponding strips from all of the disks in a RAID set. The RAID strip size must match the RAID strip size that is currently set on the RAID controller. For best performance when using hardware-based RAID systems such as SpinStor disk arrays, NetApp recommends a total stripe size of 128 KB. To determine the proper strip size, divide 128 KB by the number of data disks, excluding parity disks, in the RAID set. For instance, if the RAID set has 16 data disks, use a strip size of 8 KB (that is, 128 KB/16 disks).
-writecacheenabled {true | false}
This specifies whether the write cache is enabled. The default is true.
-status RAID_status
The RAID set status must be set to Online to enable immediate access to the RAID set after it has been created. The default is Online.
Note: Setting the status to Offline creates a RAID set but does not immediately enable its use in a storage pool.
-disks [list_of_disks]
The list of disks to be included in the RAID set is a square-bracketed, comma-separated list of disk IDs, each in the format rsubsystem_numberddisk_number, where subsystem_number indicates the RAID subsystem and disk_number indicates the specific disk drive. The maximum number of disks in a single RAID set is 16. By default, all unused disk drives (up to 16) are included. If you are using the CLI and press the Tab key after the -disks parameter, all unused disk drives (up to 16) are automatically listed.
Note: A RAID set of level 0 must have at least two (2) disks.
A RAID set of level 1 must have exactly two (2) disks.
A RAID set of level 3 must have at least three (3) disks.
A RAID set of level 5 must have at least three (3) disks.
A RAID set of level 0+1 must have at least four (4) disks.
The following command example creates RAID set named r0s0, of level 5, with a strip size of 8, using 14 disks named r0d0 through r0d15.
spinserver::> raid sets new -raidlevel 5 -stripsize 8 -writecacheenabled false -status Online -disks [r0d0, r0d1, r0d2, r0d3, r0d4, r0d5, r0d6, r0d7, r0d8, r0d9, r0d10, r0d11, r0d12, r0d13, r0d14, r0d15]
CLI:
raid sets rebuildstatus -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Rebuild Status command from the drop-down menu of the action pane.
The raid sets rebuildstatus command identifies a RAID set by the device ID assigned to it. After identification is made, the degree of completion of the rebuilding of the RAID set is displayed. Rebuilding a RAID set is necessary after a RAID set fault has been corrected. A RAID set fault occurs if a single disk in the RAID set stops functioning properly and must be replaced.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and displays the status of its rebuilding process.
spinserver::> raid sets rebuildstatus -deviceid r0s0 Action "Rebuild Status" returned with the following status: Not in progress
CLI:
raid sets show [-deviceid device_ID]
GUI: Navigate to the RAID → RAID Sets node. To display information about a specific RAID set, select it from the table and run the Show command from the drop-down menu in the action pane.
The raid sets show command identifies a specific RAID set or all RAID sets on the RAID subsystem. The command displays the following information:
Device ID
RAID level
Logical size (MB)
Physical size (MB)
Strip size (KB)
Cache line size (KB)
Initialization status
Write cache enablement status (enabled or disabled)
Online status
Number of disks in the RAID sets
List of the disks that comprise the RAID set
LongOp-in-progress status (LongOp refers to operations that take a long time to complete; for example, RAID set initialization, rebuilding, and consistency checking.)
[-deviceid device_ID]
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following example displays information about all RAID sets.
spinserver::> raid sets show Device RAID Logical Phys Size Initialized # Status ID Lvl Size Disk r0s0 5 138848 173560 true 5 Online r0s1 5 138848 173560 true 5 Online r0s2 5 138848 173560 true 5 Online r1s0 5 138848 173560 true 5 Online r1s1 5 138848 173560 true 5 Online r1s2 5 138848 173560 true 5 Online r1s3 5 138848 173560 true 5 Online r1s4 5 138848 173560 true 5 Online r1s5 5 138848 173560 true 5 Online
The following command example displays information about RAID set r0s0.
spinserver::> raid sets show -deviceid r0s0 Device ID r0s0 RAID Level 5 Logical Size (MB) 138848 Physical Size (MB) 173560 Strip Size (KB) 16 Cache Line Size (KB) 16 Initialized? true Write Cache Enabled? false Status Online # Disks 5 Disks r0d2, r0d6, r0d1, r0d5, r0d9 LongOp In Progress None
CLI:
raid sets show-disks [-deviceid device_ID]
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Show command from the drop-down menu of the action pane.
The raid sets show-disks command identifies a RAID set in the RAID subsystem with the device ID specified, or all RAID sets in the system if the -deviceid parameter is not used. The command displays a list of all disks that comprise the RAID set or sets.
[-deviceid device_ID]
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example displays informations about the disks that comprise the RAID sets.
spinserver::> raid sets show-disks
Device ID # Disks
Disk
r0s0 5 r0d2, r0d6, r0d1, r0d5, r0d9
r0s1 5 r0d10, r0d14, r0d18, r0d13, r0d17
r0s2 5 r0d22, r0d26, r0d21, r0d25, r0d29
r1s0 5 r1d66, r1d70, r1d74, r1d78, r1d82
r1s1 5 r1d86, r1d90, r1d65, r1d69, r1d73
r1s2 5 r1d77, r1d81, r1d85, r1d89, r1d93
r1s3 5 r1d34, r1d38, r1d33, r1d37, r1d41
r1s4 5 r1d42, r1d46, r1d50, r1d45, r1d49
r1s5 5 r1d54, r1d58, r1d53, r1d57, r1d61
CLI:
raid sets startbkginit -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Start BKG Initialization command from the drop-down menu of the action pane.
The raid sets startbkginit command identifies a RAID set by the device ID assigned to it. After identification is made, the background initialization of the RAID set begins.
Note: The raid sets startbkginit command works only if background initialization is enabled (background initialization is enabled by default). If background initialization is not enabled, use the raid sets startinit command.
Note: Background initialization is automatically started when a RAID set is initially used. Use this command only to force the initialization process to begin before a RAID set is used.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and begins its background initialization process.
spinserver::> raid sets startbkginit -deviceid r0s0
CLI:
raid sets startconsistencycheck -deviceid device_ID -restoreonerror {true | false}
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Start Consistency Check command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed and click Start Consistency Check.
The raid sets startconsistencycheck command identifies a RAID set with the device ID specified. After identification is made, the process of checking the consistency of the RAID set is started. If the value of the -restoreonerror parameter is set to true, the command corrects consistency errors as it discovers them.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
-restoreonerror {true | false}
If set to true, errors in consistency are corrected. The default setting is false.
The following command example identifies RAID set r0s0 and begins the process of checking the consistency of the RAID set.
spinserver::> raid sets startconsistencycheck -deviceid r0s0 -restoreonerror false
CLI:
raid sets startinit -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Start Initialization command from the drop-down menu of the action pane.
The raid sets startinit command identifies a RAID set by the device ID assigned to it. After identification is made, the initialization of the RAID set begins. Background initialization is enabled by default. Use this command only when background initialization is disabled. When background initialization is enabled, the initialization is started automatically.
Note: Initializing a RAID set with the raid sets startinit command can be a lengthy process. Depending on the size and RAID level of the RAID set, it can take up to four hours. During this time, the RAID set is unusable for other processes. For this reason, background initialization is recommended.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and begins its initialization process.
spinserver::> raid sets startinit -deviceid r0s0
CLI:
raid sets startrebuild -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Start Rebuild command from the drop-down menu of the action pane.
The raid sets startrebuild command identifies a RAID set by the device ID assigned to it. After identification is made, the rebuilding of the RAID set is started.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and starts its rebuilding process.
spinserver::> raid sets startrebuild -deviceid r0s0
CLI:
raid sets stopbkginit -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Stop BKG Initialization command from the drop-down menu of the action pane.
The raid sets stopbkginit command identifies a RAID set by the device ID assigned to it. After identification is made, the background initialization of the RAID set is stopped.
Note: The raid sets stopbkginit command works only if background initialization is enabled (background initialization is enabled by default). If background initialization is not enabled, use the raid sets stopinit command.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number specifies the RAID subsystem and raidset_number specifies the RAID set.
The following example identifies RAID set r0s0 and stops its background initialization process.
spinserver::> raid sets stopbkginit -deviceid r0s0
CLI:
raid sets stopconsistencycheck -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Stop Consistency Check command from the drop-down menu of the action pane.
The raid sets stopconsistencycheck command identifies a RAID set with the device ID specified. After identification is made, the process of checking the consistency of the RAID set is stopped.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number specifies the RAID subsystem and raidset_number specifies the RAID set.
The following command example identifies RAID set r0s0 and stops the process of checking the consistency of the RAID set.
spinserver::> raid sets stopconsistencycheck -deviceid r0s0
CLI:
raid sets stopinit -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select a RAID set from the table and run the Stop Initialization command from the drop-down menu of the action pane.
The raid sets stopinit command identifies a RAID set by the device ID assigned to it. After identification is made, the initialization of the RAID set is stopped. Use this command only when background initialization is disabled and an initialization of the RAID set was previously started by using the raid sets startinit command. When background initialization is enabled, use the raid sets stopbkginit command.
-deviceid device_ID
The device identification is in the format of rsubsystem_numbersraidset_number, where subsystem_number specifies the RAID subsystem and raidset_number specifies the RAID set.
The following command example identifies RAID set r0s0 and halts its initialization process.
spinserver::> raid sets stopinit -deviceid r0s0
CLI:
raid sets stoprebuild -deviceid device_ID
GUI: Navigate to the RAID → RAID Sets node, then select the appropriate RAID set from the table and run the Stop Rebuild command from the drop-down menu of the action pane.
The raid sets stoprebuild command identifies a RAID set by the device ID assigned to it. After identification is made, the rebuilding of the RAID set is stopped.
-deviceid device_ID
The device identification is in the format rsubsystem_numbersraidset_number, where subsystem_number indicates the RAID subsystem and raidset_number indicates the specific RAID set.
The following command example identifies RAID set r0s0 and halts its rebuilding process.
spinserver::> raid sets stoprebuild -deviceid r0s0
To manage RAID subsystems, use the following raid subsystems commands.
disablesmart
discoverenclosures
dumpconfig
enablesmart
events
modify
reset
show
updatediskfirmware
CLI:
raid subsystems disablesmart -id ID
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Disable S.M.A.R.T. command from the drop-down menu of the action pane.
The raid subsystems disablesmart command disables SMART for all the disk drives of a RAID subsystem.
Note: SMART is enabled by default.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
The following command example disables SMART for the RAID subsystem r0.
spinserver::> raid subsystems disablesmart -id r0
CLI:
raid subsystems discoverenclosures -id ID
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Discover Enclosures command from the drop-down menu of the action pane.
The raid subsystems discoverenclosures command forces the RAID subsystem to recognize a newly attached RAID or expansion JBOD disk enclosure.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
The following command example forces a RAID subsystem named r0 to recognize a newly attached disk enclosure.
spinserver::> raid subsystems discoverenclosures -id r0
CLI:
raid subsystems dumpconfig -id ID -file file_path
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Dump Configuration command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed and click Dump Configuration.
To provide Technical Support representatives with configuration information to assist you in debugging a SpinServer system's RAID controllers, use the raid subsystems dumpconfig command. After you use the raid subsystems dumpconfig command, the specified file contains extra debugging information that is useful for technicians and support personnel.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
-file file_path
This specifies the file that is to contain the configuration information.
The following command example prints the configuration information for the RAID subsystem named r0 to a file named /tmp/dump.
spinserver::> raid subsystems dumpconfig -id r0 -file /tmp/dump
CLI:
raid subsystems enablesmart -id ID
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Enable S.M.A.R.T. command from the drop-down menu of the action pane.
The raid subsystems enablesmart command enables SMART for all the disk drives of a RAID subsystem. SMART is enabled by default.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
The following command enables SMART for the RAID subsystem r0.
spinserver::> raid subsystems enablesmart -id r0
CLI:
raid subsystems events -id ID -number number_of_events
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Raid Events command from the drop-down menu of the action pane. Enter the appropriate value into the table that is displayed, then click Raid Events.
The raid subsystems events command displays events that have occurred on a RAID subsystem. This is useful for diagnosing problems with RAID arrays.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
-number number_of_events
This specifies the number of events to be displayed. If this value is higher than the number of messages from the RAID controller, then all of the messages from the controller are displayed.
The following command displays the first 10 events for the RAID subsystem r0.
spinserver::> raid subsystems events -id r0 -number 10 Action "Raid Events" returned with the following status: 0: System (sys: r0) started successfully.[12 Aug 09:43:19] 1: Automatic reboot count has changed on System (sys: r0).[12 Aug 09:43:19] 2: Dual controllers enabled on System (sys: r0).[12 Aug 09:43:19] 3: Updated partner's status on System (sys: r0).[12 Aug 09:43:19] 4: Dual controllers entered nexus on System (sys: r0).[12 Aug 09:43:19] 5: System (sys: r0) started successfully.[12 Aug 09:43:19] 6: Automatic reboot count has changed on System (sys: r0).[12 Aug 09:43:19] 7: Dual controllers enabled on System (sys: r0).[12 Aug 09:43:19] 8: Updated partner's status on System (sys: r0).[12 Aug 09:43:19] 9: Controller started completed on System (sys: r0).[12 Aug 09:43:19]
CLI:
raid subsystems modify -id ID -bkginit {true | false} -rebuildrate rebuild_rate
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The raid subsystems modify command changes the background initialization setting and rebuild rate for a RAID subsystem.
-id ID
The device identification is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
-bkginit {true | false}
To enable background initialization, use true as the argument. To disable the background initialization process, use false as the argument. The default is true.
-rebuildrate rebuild_rate
This specifies the percentage of the RAID controller's CPU that is used for RAID rebuilding. The default setting is 1.
The following example disables background initialization and sets the rebuild rate to 5 percent for the RAID subsystem r0.
spinserver::> raid subsystems modify -id r0 -bkginit false -rebuildrate 5
CLI:
raid subsystems reset -id ID
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Reset command from the drop-down menu from the action pane.
The raid subsystems reset command resets the RAID subsystem to restore the default settings. This is necessary in the event of an error.
-id ID
The ID of the RAID subsystem is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
CLI:
raid subsystems show [-id ID]
GUI: Navigate to the RAID → RAID Subsystems node. To display information about a specific RAID subsystem, select it from the table and run the Show command from the drop-down menu of the action pane.
The raid subsystems show command identifies a RAID subsystem or all RAID subsystems on the system. The command displays the following information about the RAID subsystems:
RAID subsystem ID
Status (online or critical)
List of host connections
Names of servers connected to the RAID subsystem
RAID controllers connected to the RAID subsystem
RAID sets configured on the RAID subsystem
RAID enclosures on the RAID subsystem
Battery backup units connected to the RAID subsystem
Number of disk enclosures in the RAID subsystem
Number of disks included in the RAID subsystem
Number of RAID sets included in the RAID subsystem
Background initialization setting (true or false)
[-id id]
The RAID subsystem ID is in the format rsubsystem_number, where subsystem_number indicates the RAID subsystem.
The following example displays information about all RAID subsystems:
spinserver::> raid subsystems show ID Status Host Connections # Encs # Disks # RAIDs r0 Critical 1 15 3 r1 Critical 2 30 6
The following command example displays information about RAID subsystem r0:
spinserver::> raid subsystems show -id r0 ID r0 Status Critical Host Connections SpinServers Connected Server1 Controllers r0c0, r0c1 RAID sets r0s0, r0s1, r0s2 Enclosures r0e1 Battery r0b1 # Enclosures 1 # Disks 15 # RAID sets 3 Background Init false
CLI:
raid subsystems updatediskfirmware -id ID -imagefile path
GUI: Navigate to the RAID → RAID Subsystems node, then select the appropriate RAID subsystem from the table and run the Update Disk Firmware command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed and click Update Disk Firmware.
The raid subsystems updatediskfirmware command updates the firmware of all the disk drives in a specified RAID subsystem. Note the following before upgrading disk firmware on a RAID subsystem:
| Caution: |
|
Upgrading the disk firmware can possibly but rarely cause data loss. It is recommended that you back up all of the data on the RAID subsystem or copy it to another storage pool before upgrading the disk firmware. |
If a RAID set is in a critical state, it is not fault tolerant, and its disks' firmware cannot be upgraded until the RAID set is rebuilt.
If a failure occurs during the upgrade process, some of the disks can have the new firmware while other disks do not. In addition, one of the RAID sets can become critical because it has lost use of a disk. To restore normal operation, use a standard recovery technique such as rebuilding the RAID set by using a spare disk.
To modify the firmware on a specific disk, use the raid diskdrives updatefirmware command.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.